feat: update metatag to recommended release #495
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stephen-cox
approved these changes
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
I couldn't work out why coding standards failed on https://github.com/localgovdrupal/localgov_microsites_project/actions/runs/11678582582/job/32518280525 and localgov_news stays at 2.3.8 and doesn't go to 2.3.10.
After having some free time it turns out it was because metatag is using version 1 and not set to the latest recommended release, version 2 (https://www.drupal.org/project/metatag).
metatag is also in https://github.com/localgovdrupal/localgov_core/blob/2.x/composer.json#L13 so there is a question around whether we just remove it from the profile as we already include localgov_core as a dependency